Authentication, authorization, and/or accounting of power-consuming devices

ABSTRACT

Systems and methods for authenticating, authorizing, and/or accounting for a power-consuming device to access a power source are described. A power access controller can manage the power source and authenticate and/or authorize the power-consuming device to access the power source based on, for example, a power profile of the power-consuming device. The power profile can indicate categories of devices for the power-consuming device, the manufacturer of the power-consuming device, and/or the device&#39;s expected power consumption. Accounting of an amount of power consumed by the power-consuming device can also be performed.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of pending U.S. patent applicationSer. No. 15/716,697, filed Sep. 27, 2017, now U.S. Pat. No. 10,338,113,issued Jul. 2, 2019, and entitled “Authentication, Authorization, and/orAccounting of Power-Consuming Devices,” which is a continuation ofgranted U.S. Pat. No. 9,804,210, filed Aug. 31, 2015 and entitled“Authentication, Authorization, and/or Accounting of Power-ConsumingDevices.” The prior applications are incorporated herein by reference intheir entirety.

BACKGROUND

Power outlets and chargers are often accessible to the public. Forexample, chargers may be located in a public garage, or power outletsmay be located on the outside of a home. Because these outlets andchargers are accessible to the public, power may be taken by any devicewithout first performing authentication or authorization. Moreover,accounting of the power consumed by these devices may be difficult.

SUMMARY

This summary is not intended to identify critical or essential featuresof the disclosures herein, but instead merely summarizes certainfeatures and variations thereof. Other details and features will also bedescribed in the sections that follow.

A method described herein may comprise receiving, from a power-consumingdevice, a power profile indicating an expected power consumption of thepower-consuming device. The expected power consumption may comprise atleast one of a rated power consumption and a historical powerconsumption of the power-consuming device. It may be determined whetherthe expected power consumption of the power-consuming device exceeds athreshold power consumption. If the expected power consumption of thepower-consuming device does not exceed the threshold power consumption,access to a power source may be granted to the power-consuming device.One or more embodiment described herein may be performed by at least oneof a power outlet and a charger, and receiving the power profile may beperformed in response to the power-consuming device being connected tothe at least one of the power outlet and the charger.

The power profile may indicate a manufacturer of the power-consumingdevice. Moreover, the method may comprise determining whether devicesmanufactured by the manufacturer of the power-consuming device areauthorized to access the power source. Granting the power-consumingdevice access to the power source may be performed in response todetermining that the expected power consumption of the power-consumingdevice does not exceed the threshold power consumption and in responseto determining that devices manufactured by the manufacturer of thepower-consuming device are authorized to access the power source.

The power profile may indicate a category of the power-consuming device.Moreover, the method may comprise determining whether devicescategorized in the category of the power-consuming device are authorizedto access the power source. Granting the power-consuming device accessto the power source may be performed in response to determining that theexpected power consumption of the power-consuming device does not exceedthe threshold power consumption and in response to determining thatdevices categorized in the category of the power-consuming device areauthorized to access the power source.

In some aspects, the method may comprise determining, based on theexpected power consumption of the power-consuming device, whether acircuit of the power source would be overloaded if the power-consumingdevice is granted access to the power source. Granting thepower-consuming device access to the power source may be performed inresponse to determining that the expected power consumption of thepower-consuming device does not exceed the threshold power consumptionand in response to determining that the circuit of the power sourcewould not be overloaded if the power-consuming device is granted accessto the power source.

After the power-consuming device is granted access to the power sourceand in response to determining that a power consumption of thepower-consuming device exceeds the expected power consumption of thepower-consuming device by a second threshold power consumption, accessto the power source may be denied.

The method may also comprise authenticating the power-consuming device.Prior to authenticating the power-consuming device, a pulse may beprovided to the power-consuming device. The pulse may be configured toinitiate the authenticating. Granting the power-consuming device accessto the power source may be performed in response to determining that theexpected power consumption of the power-consuming device does not exceedthe threshold power consumption and in response to authenticating thepower-consuming device.

A method described herein may comprise sending, by a power-consumingdevice and to a computing device, a power profile indicating an expectedpower consumption of the power-consuming device. In response toreceiving an indication from the computing device that thepower-consuming device has been granted access to a power source basedon the expected power consumption of the power-consuming device, thepower-consuming device may access the power source. In some aspects, thecomputing device may comprise at least one of a power outlet and acharger, and sending the power profile may be performed in response tothe power-consuming device being connected to the at least one of thepower outlet and the charger.

The power profile may indicate a manufacturer of the power-consumingdevice. Moreover, the power-consuming device accessing the power sourcemay be performed in response to receiving the indication from thecomputing device that the power-consuming device has been granted accessto the power source based on the expected power consumption of thepower-consuming device and based on a determination that devicesmanufactured by the manufacturer of the power-consuming device areauthorized to access the power source.

The power profile may indicate a category of the power-consuming device.Moreover, the power-consuming device accessing the power source may beperformed in response to receiving the indication from the computingdevice that the power-consuming device has been granted access to thepower source based on the expected power consumption of thepower-consuming device and based on a determination that devicescategorized in the category of the power-consuming device are authorizedto access the power source.

In some aspects, the power-consuming device may access the power sourcein response to receiving the indication from the computing device thatthe power-consuming device has been granted access to the power sourcebased on the expected power consumption of the power-consuming deviceand based on a determination that a circuit of the power source wouldnot be overloaded if the power-consuming device is granted access to thepower source.

After the power-consuming device accesses the power source, thepower-consuming device may send to the computing device a present powerconsumption of the power-consuming device. The power-consuming devicemay receive an indication from the computing device that thepower-consuming device has been denied access to the power source basedon a determination that the present power consumption of thepower-consuming device exceeds the expected power consumption of thepower-consuming device by a second threshold power consumption.

The method may also comprise authenticating the power-consuming device.For example, in response to the power-consuming device receiving a pulsefrom the computing device, the power-consuming device may initiate anauthentication session.

A power-consuming device described herein may comprise a processor, apower supply, and memory storing computer-executable instructions. Whenthe instructions are executed by the processor, the power-consumingdevice may receive a charge pulse from a power access controller. Thepower-consuming device may charge the power supply using the chargepulse. The charged power supply may authenticate or authorize thepower-consuming device to access a power source managed by the poweraccess controller. The memory may store additional computer-executableinstructions that, when executed by the processor, cause thepower-consuming device to access the power supply responsive toreceiving a message indicating that the power-consuming device isauthenticated or authorized to access the power source. In some aspects,the power-consuming device may send, to the power access controller, amessage indicating that a charge level of the power supply of thepower-consuming device is below a threshold charge level. Thepower-consuming device may receive a second charge pulse from the poweraccess controller.

The foregoing methods and other methods described herein may beperformed by a system, a computing device, a computer readable mediumstoring computer-executable instructions for performing the methods,and/or an apparatus having a processor and memory storingcomputer-executable instructions for performing the methods.

BRIEF DESCRIPTION OF THE DRAWINGS

Some features herein are illustrated by way of example, and not by wayof limitation, in the figures of the accompanying drawings and in whichlike reference numerals refer to similar elements.

FIG. 1 illustrates an example network of devices according to one ormore illustrative aspects of the disclosure.

FIG. 2 illustrates an example hardware and software platform on whichvarious elements described herein can be implemented.

FIG. 3 illustrates an example method of authenticating a deviceattempting to access a power source according to one or moreillustrative aspects of the disclosure.

FIG. 4 illustrates an example method of authorizing a device attemptingto access a power source according to one or more illustrative aspectsof the disclosure.

FIG. 5 illustrates an example method of accounting for a deviceaccessing a power source according to one or more illustrative aspectsof the disclosure.

DETAILED DESCRIPTION

FIG. 1 illustrates an example network of devices 100 according to one ormore illustrative aspects of the disclosure. The network 100 may be anytype of information and power distribution network, and information maybe communicated between the devices via satellite, telephone, cellular,wireless, power line communication, etc. One example may be an opticalfiber network, a coaxial cable network or a hybrid fiber/coax (HFC)distribution network. Another example may be a power transmission anddistribution network having power line communication capabilities. Suchnetworks 100 may use power/communication links 101, 102, and 103 (e.g.,coaxial cables, optical fibers, wireless connections, power linenetworks, etc.) to connect devices at multiple locations, such as afirst location 105, a second location 120, and/or a third location 130.

The first location 105 may include a power access controller 115 (e.g.,a power outlet, an adapter that can be plugged into the power outlet, awired charger, a wireless charger for inductive or wireless charging,etc.) for providing (or granting access to) power to power-consumingdevices 110. The first location 105 may comprise a home, a businesslocation, an airport, a vehicle charging station, a battery chargingstation, a parking garage or parking lot, and the like. The power accesscontroller 115 may be integrated into the power outlet or charger. Forexample, the controller 115 may be built into a building's power supplyor power outlet and be used to control access to the power supply oroutlet. Alternatively, the power access controller 115 may be a deviceseparate from the power supply or power outlet. For example, thecontroller 115 may comprise an adapter (e.g., expander) and be pluggedinto the power outlet.

The power-consuming device 110 may comprise a mobile phone, a tablet, alaptop, a desktop computer, a vehicle, a thermostat, a householdappliance, a television, or any other electronic device that consumespower. The device 110 may be electrically connected to the power accesscontroller 115 via a wire or wireless connection 103. The connection 103may be used to communicate information between the power accesscontroller 115 and the power-consuming device 110. The connection 103may also be used to provide power to the power-consuming device 110 from(or via) the power access controller 115. In some aspects, the powerprovided to the power-consuming device 110 may be used to charge thepower-consuming device's power supply, such as a battery or a capacitor.The power-consuming device 110 may include a client application used toauthenticate and/or authorize the power-consuming device 110 to receivepower from (or via) the power access controller 115 and/or to accountfor power consumed by the device 110. Examples of authentication,authorization, and accounting will be described in further detail below.

The network 100 may optionally include a second location 120 having amaster power controller 125. The second location 120 may be a locationdifferent from the first location 105, such as a central office, abackend network, a headend, a billing system, and the like. The poweraccess controller 115 may act as a gateway (e.g., router) between thepower-consuming device 110 and the master power controller 125, and themaster power controller 125 may be used to authenticate and/or authorizethe power-consuming device 110 to access a power source and/or toaccount for the amount of power consumed by the power-consuming device110 from the power source. The master power controller 125 may be usedto manage multiple power access controllers 115 at the same location(e.g., the vehicle chargers at a parking garage or the outlets in auser's home) or different locations (e.g., one or more outlets in auser's home and one or more outlets in a neighbor's home).

As previously described, the master power controller 125 and the poweraccess controller 115 may communicate over a wired or wirelessconnection 101. Exemplary wired connections include an in-band powerline connection or a separate data connection, such as Ethernet, coaxialcable, optical fiber, etc. Exemplary wireless connections include Wi-Fi(e.g., 802.11x), ZigBee, Bluetooth, cellular, etc. If the power accesscontroller 115 is used to authenticate, authorize, and/or performaccounting for the power-consuming device 110, the master powercontroller 125 might not be used for authentication, authorization, oraccounting.

The network 100 may optionally include a third location 130 having apower source 135. The power source 135 may comprise an electric utilitygeneration, transmission, and/or distribution facility. The power source135 may provide electric power to the first location 105 via connection102, and the power access controller 115 and/or power-consuming device110 may have access to the electric power at the first location 105. Ifthe power source that provides power to the power-consuming device 110is integrated in the power access controller 115, the power source 135might not be used and thus is optional.

FIG. 2 illustrates general hardware and software elements that can beused to implement any of the various devices discussed herein (e.g.,power-consuming device 110, power access controller 115, master powercontroller 125, or power source 135). The computing device 200 mayinclude one or more processors 201, which may execute instructions of acomputer program to perform any of the features described herein. Theinstructions may be stored in any type of computer-readable medium ormemory, to configure the operation of the processor 201. For example,instructions may be stored in a read-only memory (ROM) 202, randomaccess memory (RAM) 203, hard drive, removable media 204, such as aUniversal Serial Bus (USB) drive, compact disk (CD) or digital versatiledisk (DVD), floppy disk drive, or any other desired electronic storagemedium. Instructions may also be stored in an attached (or internal)hard drive 205. The computing device 200 may include one or more outputdevices, such as a display 206 (or an external television), and mayinclude one or more output device controllers 207, such as a videoprocessor. There may also be one or more user input devices 208, such asa remote control, keyboard, mouse, touch screen, microphone, etc.

The computing device 200 may also include one or more network interfaces209, such as input/output circuits (such as a network card) tocommunicate with an external network 210 or other devices. The interface209 may be a wired interface, wireless interface, or a combination ofthe two. In some embodiments, the interface 209 may include a modem(e.g., a cable modem), and the network 210 may include the communicationlinks 101 or 102 discussed above, the external network 210, an in-homenetwork, a provider's wireless, coaxial, fiber, or hybrid fiber/coaxialdistribution system (e.g., a DOCSIS network), or any other desirednetwork. The computing device 200 may communicate with the externalnetworks 210 or other devices using one or more communication protocols,such as wired communication protocols and wireless communicationprotocols (e.g., Wi-Fi, Bluetooth, ZigBee, Z-Wave, etc.).

FIG. 3 illustrates an example method of authenticating a power-consumingdevice 110 attempting to access a power source 135 according to one ormore illustrative aspects of the disclosure. The steps described withrespect to FIG. 3 may be performed by one or more computing devices,such as the power access controller 115, the master power controller125, and/or the power source 135. As previously explained, the masterpower controller 125 and power source 135 are optional if the poweraccess controller 115 is configured to authenticate and authorizeconnected power-consuming devices, account for power consumed bypower-consuming devices, and to provide power to power-consumingdevices.

Additionally or alternatively, the master power controller 125 may beconfigured to authenticate and/or authorized power-consuming devices toaccess power and/or to account for the power consumed. The power source135 may be configured to provide power, such as AC or DC power, to thelocation 105, and the power access controller 115 may be configured toprovide that power to power-consuming devices 110. The master powercontroller 125 may be configured to authenticate, authorize, and/oraccount for power-consuming devices' power consumption. For the sake ofconvenience, the steps described with respect to FIG. 3 will generallybe described as being performed by the power access controller 115.However, the power access controller 115, the master power controller125, and the power source 135 may be configured to work together toperform one or more of the steps described with respect to FIG. 3.

Initially, the power access controller 115 may prevent access to thepower source 135 at the first location 105 (or an outlet or charger atthe first location 105). For example, a power outlet might initially beturned off so that it does not supply power to devices plugged in to theoutlet (e.g., a power-consuming device 110).

In step 305, the power access controller 115 may determine whether apower-consuming device 110 has been detected, such as if the device 110has been plugged into a power outlet (or has been wirelessly connectedto a wireless charger). If not (step 305: N), the power accesscontroller 115 may wait until a device 110 has been detected in step305. If a power-consuming device 110 has been detected (step 305: Y),the power access controller 115 may proceed to step 310.

In step 310, the power access controller 115 may provide a pulse to thedevice 110. The pulse may be used to initiate authentication of thedevice 110. In some aspects, the pulse may comprise a charge pulse, suchas a low voltage (e.g., 5V) DC or AC charge used to charge a battery,capacitor, or other power supply in the device 110. The device 110 mayuse the received charge in the power supply for the authenticationand/or authorization process. The charge pulse may be beneficial if thedevice 110 does not have a large power supply (e.g., a small capacitor),the power supply is completely discharged (e.g., the battery isdischarged), or the power supply does not have enough charge to completethe authentication and/or authorization process.

In step 315, the power access controller 115 may initiate authenticationof the device 110, or the device 110 may initiate an authenticationsession in response to receiving the pulse from the power accesscontroller 115. During authentication, the device 110 may transmit anidentifier, such as its credentials, Media Access Control (MAC) address,Internet Protocol (IP) address, International Mobile Station EquipmentIdentity (IMEI) number, manufacturer ID, serial number, or other uniqueidentifier, to the power access controller 115. The power accesscontroller 115 may forward the device's identifier to the master powercontroller 125, and the master power controller 125 may authenticate thedevice 110 using the received credentials. If mutual authentication isused, the power access controller 115 and/or master power controller 125may also transmit its credentials to the device 110 for authentication.In the foregoing example, the master power controller 125 mayauthenticate the device 110, with the power access controller 115 actingas a gateway for exchanging information between the master powercontroller 125 and the device 110. In alternative aspects, the poweraccess controller 115 may itself authenticate the device 110 withouttransmitting the device's identifier to the master power controller 125.

The authentication session may be secured (e.g., encrypted) using aconventional encryption technique, such as the Transport Layer Security(TLS) protocol, the Secure Sockets Layer (SSL) protocol, or asymmetric(public/private key pair) or symmetric encryption keys. As explainedabove, the information transmitted between the device 110, the poweraccess controller 115, and the master power controller 125 may be via awired or wireless connection. For example, if wired power linecommunication is used, the communication may use a one-wire serialcommunication protocol over the not yet hot lead.

In step 320, the power access controller 115 may determine whether thedevice 110 has been authenticated. If the device 110 has beenauthenticated (step 320: Y), the power access controller 115 may proceedto step 405 described with respect to FIG. 4 for authorization, whichwill be described in further detail in the examples below. If the device110 has not been authenticated (step 320: N), the power accesscontroller 115 may proceed to step 325.

In step 325, the power access controller 115 may determine whether toend the authentication session with the device 110. The power accesscontroller 115 may end the authentication session if authenticationcannot be completed, for example based on a timeout, if the power accesscontroller 115 (or master power controller 125) cannot authenticate thedevice 110 based on the received credentials, etc. If the authenticationsession is to be ended (step 325: Y), the power access controller 115may proceed to step 425 described with respect to FIG. 4 and deny thedevice 110 access to the power source 135.

The authentication steps described with respect to FIG. 3 may be used tosecure outlets or chargers accessible to the public, such as a vehiclecharger in a parking garage or a power outlet outside of a user's home.By authenticating (and authorizing) devices before granting access tothe power source 135, theft of power might be prevented, and the owneror manager of the charger or outlet would not need to pay attention tothe state of the publicly accessible charger or outlet. At the sametime, authenticated (and authorized) devices may still access the powersource 135 via the charger or outlet. For example, a user's neighbor maybe permitted to use the user's outside outlet. Residents of an apartmentcomplex above a parking garage may be permitted to use vehicle chargersin the parking garage.

Returning to FIG. 3, if the authentication session is not to be ended(step 325: N), the power access controller 115 may proceed to steps 330and 335 to determine whether to provide a charge pulse to the device110. Steps 330 and 335, as with all steps, are optional and might not beperformed if the device 110 has its own power supply (e.g., a battery)or the power supply has enough power to complete authentication.

In step 330, the power access controller 115 may determine whether thedevice's power supply (e.g., a battery, capacitor, etc.) level is belowa threshold. During authentication, the device 110 may notify the poweraccess controller 115 if the level of its power supply is below thethreshold. If the level is not below the threshold (step 330: N), thepower access controller 115 may return to step 320 to determine whetherthe device 110 has been authenticated. If the level is below thethreshold (step 330: Y), the power access controller 115 may proceed tostep 335. The amount of power used to complete authentication may varyby device, and the threshold may be varied accordingly so that thedevice 110 will have enough power to complete authentication.

In step 335, the power access controller 115 may provide a charge pulseto the device 110. The device 110 may use the charge pulse to charge itspower supply, which may be used to power the device 110 duringauthentication. The power access controller 115 may return to step 320to determine whether the device 110 has been authenticated. In someaspects, instead of providing the device 110 with a charge pulse basedon the level of charge, the power access controller 115 may periodicallyprovide charge pulses to the device 110 (e.g., every 5 seconds) duringauthentication (or during authorization, as will be described below).Additionally or alternatively, the power access controller 115 mayprovide a charge pulse based on a timeout, such as if the power accesscontroller 115 has not received communications from the device 110 for athreshold amount of time. Once the device 110 is authenticated (step320: Y), the power access controller 115 may proceed to the stepsdescribed with respect to FIG. 4 for authorization of the device 110.

FIG. 4 illustrates an example method of authorizing a power-consumingdevice 110 attempting to access a power source 135 according to one ormore illustrative aspects of the disclosure. The steps described withrespect to FIG. 4 may be performed by one or more computing devices,such as the power access controller 115, master power controller 125,and/or power source 135. For the sake of convenience, the stepsdescribed with respect to FIG. 4 will generally be described as beingperformed by the power access controller 115.

In step 405, the power access controller 115 may receive a power profilefrom the device 110. The power profile may comprise an identifier forthe device 110, such as a network address (e.g., MAC address, IPaddress, etc.) or other device identifier (e.g., a manufacturer ID,device model name, serial number, certificate, etc.). The power profilemay also identify the device's category or categories, such as householdappliance, vehicle, mobile phone, mobile device, television, laptopcomputer, etc. For example, if the device 110 is a mobile phone, thepower profile may identify the categories as mobile phone and mobiledevice. If the device 110 is a laptop computer, the power profile mayidentify the categories as laptop computer and mobile device. If thedevice 110 is a refrigerator, the power profile may identify thecategory as household appliance. The power profile may also identify themanufacturer of the device 110.

The power profile may also indicate the device's power consumption(e.g., expected power consumption, such as rated power consumption orhistorical power consumption). For example, the power profile mayindicate the device's average power consumption (in Watts) over a periodof time, such as 5 days. The power profile may also indicate thedevice's peak power consumption (e.g., in Watts), such as switch-on peakpower consumption or maximum power consumption. The power profile mayalso indicate the power factor (e.g., power efficiency) of the device110.

The power profile may indicate other operating parameters for the device110. For example, the power profile may indicate the normal, minimum,and/or maximum operating voltages for the device 110 or a component inthe device 110, such as a power supply. The power profile may indicatevoltage and/or current tolerances for the device 110 or a component inthe device 110, such as over-voltage tolerance, under-voltage tolerance,and over-current tolerance. If the device 110 has its own protectivedevice (e.g., a breaker or a fuse) the power profile may includeinformation on a protective device. For example, the power profile mayindicate the fuse or breaker type, fuse or breaker rating (e.g., involts and/or amps), status of the fuse (e.g., operational, triggered,should be replaced, etc.). The power profile may also indicate whetherthe power supply of the device 110 supports AC and/or DC power. If thedevice 110 supports AC power, the power profile may indicate thefrequencies supported (e.g., 50 Hz, 60 Hz, etc.) and/or the voltagessupported (e.g., 110 V, 230 V, etc.). The power profile may includetolerances for any of the following: line noise immunity for aDC-powered device 110 (units may be in, e.g., milliseconds), cycle dropsfor an AC-powered device 110 (units may be in, e.g., milliseconds),interruptions for a DC-powered device (units may be in, e.g.,milliseconds), voltage dip, and/or heat dissipation rating (units may bein, e.g., British thermal unit or BTU).

In some aspects, the power access controller 115 may retrieve, from adatabase, any information that is missing in the device's power profile.For example, the power access controller 115 may use the rated powerconsumption of the device 110 to determine whether to authorize thedevice 110 to access the power source 135 (in steps 410 and 415, as willbe described below). However, the power profile for the device 110 mightnot have included the rated power consumption of the device 110. In thisexample, the power access controller 115 may use other informationprovided by the device 110 to determine the missing information. Forexample, the power access controller 115 may query a database, such as amanufacturer's database, with information identifying the device 110(e.g., the serial number, IMEI, device model and number, etc.) and arequest for the missing information. In response, the database may sendthe requested information, such as the rated power consumption of thedevice 110, to the power access controller 115.

In step 410, the power access controller 115 may determine whether thedevice 110 should be authorized to access the power source 135 based onthe received power profile. In alternative aspects, the power accesscontroller 115 may send the device power profile to the master powercontroller 125, and the master power controller 125 may determinewhether to authorize the device 110 based on the received power profile.

Authorization may be based on the identity of the manufacturer of thedevice 110. The power access controller 115 may store or have access toa stored list of manufacturers authorized to access the power source135. For example, Manufacturer A and Manufacturer B may be on the listof authorized manufacturers, whereas Manufacturer C might not be on thelist. If the power access controller 115 determines that device 110 wasmanufactured by Manufacturer A or Manufacturer B (e.g., based on anidentifier provided by the device 110 during an authentication orauthorization session), the power access controller 115 may determinethat device 110 is authorized to access the power source 135 (step 410:Y). On the other hand, if the device 110 was manufactured byManufacturer C, the power access controller 115 may determine thatdevice 110 is not authorized to access the power source 135 (step 410:N).

Authorization may additionally or alternatively be based on the categoryor categories of the device 110. For example, mobile devices may beauthorized to access the power source 135, whereas household appliancesmight not be authorized to access the power source 135. Authorizationmay additionally be based on the location 105 of the power accesscontroller 115 (and device 110). For example, the power accesscontroller 115 may be located inside of an airport, such as within oneof the airport terminals. The power access controller 115 may permitdevices categorized as mobile phones, mobile devices, and laptopcomputers to access the power source 135 within the airport. On theother hand, the power access controller 115 might prevent householdappliances, vehicles, and televisions from accessing the power source135 within the airport. If the power access controller 115 is located ina garage of the airport, the controller 115 may grant access tovehicles, mobile phones, mobile devices, and laptop computers, but denyaccess to household appliances and televisions. If the power accesscontroller 115 is located in a home, the controller 115 may grant accessto mobile phones, mobile devices, laptop computers, householdappliances, and televisions.

Authorization may additionally or alternatively be based on the expectedpower consumption of the device 110 being below a threshold consumption.The power access controller 115 may store or have access to storedthresholds for average power consumption, peak power consumption, andmaximum power consumption. If the device's power profile indicates thatthe device's power consumption exceeds one, two, or all three of thesethresholds, the controller 115 may determine that device 110 is notauthorized to access the power source 135 (step 410: N). Otherwise, thepower access controller 115 may determine that the device 110 isauthorized to access the power source 135 (step 410: Y). For example,assume that a threshold for peak power consumption is 105 watts. Assumethe device 110 comprises a laptop computer, and the power profile forthe laptop indicates that the peak power consumption for the laptop is100 watts. In this example, the power access controller 115 maydetermine that the laptop computer 110 is authorized to access the powersource 135 because the peak power consumption of the laptop is less thanthe threshold (step 410: Y). In some aspects, authorization may be usedfor circuit overload protection based on current power consumption, aswill be described below in reference to step 415.

Authorization may additionally or alternatively be based on any of theoperating parameters included in the power profile or retrieved from adatabase (e.g., operating voltages and/or currents, fuse or breakerinformation, frequencies and/or voltages supported by the device 110,etc.). For example, if the device's operating voltage (e.g., 5V) exceedsa threshold operating voltage (e.g., 4V), the controller 115 maydetermine that device 110 is not authorized to access the power source135 (step 410: N). If the device's power profile indicates that thedevice 110 does not support DC power, and the power source 135 is a DCpower source, the controller 115 may determine that device 110 is notauthorized to access the power source 135 (step 410: N). If the device'spower profile indicates that the device 110 supports up to 120V ACpower, and the power source 135 is a 230V AC power source, the poweraccess controller 115 may determine that device 110 is similarly notauthorized to access the power source 135 (step 410: N). If the device'spower profile indicates that the switch or fuse of the device 110 shouldbe replaced, the controller 115 may determine that the device 110 is notauthorized to access the power source 135 (step 410: N) until the switchor fuse is replaced. The above examples are merely exemplary, and any ofthe operating parameters described herein may be used to authorize thedevice 110 (or deny the device 110) to access the power source 135.

In step 415, the power access controller 115 may determine whether theaddition of the device 110 to the power source 135 would overload thepower supply circuit. For example, an overload may occur if a circuitbreaker or switch is tripped. Overload may also occur if powerconsumption at a particular outlet or within the home exceeds athreshold consumption. The power access controller 115 may measure, inreal time, the present power drawn from the power source 135, the powerdrawn by devices at the location 105, and/or power drawn at theparticular power outlet or connection point for the device 110. Thepower access controller 115 may also determine the maximum or thresholdpower consumption for the power source 135, the location 105, and/or theparticular outlet. Moreover (and as previously explained), the poweraccess controller 115 may determine the expected average, peak, ormaximum power consumption of the device 110 based on its power profile.

The threshold power consumption may be set to a rating of the circuitbreaker or switch, such as the maximum power or current that the breakercan handle before it is tripped (e.g., a maximum power of 2.4 kilowatts,a maximum current of 40 Amps, etc.). The threshold may also be set toprovide a margin (e.g., a safety margin) for the breaker or switch. Forexample, if the maximum power of the breaker is 2.4 kW, the thresholdmay be set to a value lower than 2.4 kW, such as 2 kW. As anotherexample, if a 5% margin is used, the threshold may be set to 2.28 kW.

In some aspects, several power access controllers 115 may be groupedtogether and managed by a master power controller 125 or power source135. The threshold power consumption may be a collective threshold powerconsumption for all of the power access controllers 115 in the group.For example, the collective threshold power consumption may be 10 kW. Iffour power access controllers 115 are in the group, the power accesscontrollers 115 may each be assigned an equal threshold powerconsumption (e.g., 2.5 kW threshold). Alternatively, the assignedthresholds might not be equal. For example, the first two power accesscontrollers 115 may each be assigned a 3 kW threshold, and the last twopower access controllers 115 may each be assigned a 2 kW threshold. Ifthe power access controllers 115 are at different locations, assigningthe thresholds may be based on the type of each location. For example, apower access controller 115 at a commercial location, such as an airportterminal or parking garage, may be assigned a higher threshold, such as3 kW. A power access controller 115 at a residential location, such as ahome, may be assigned a lower threshold, such as 2 kW.

Using the above information, the power access controller 115 maydetermine whether providing the device 110 with access to the powersource 135 would overload the power supply circuit. For example, thecontroller 115 may determine whether the power that the device 110 isexpected to consume exceeds the available (e.g., spare) power on thepower supply circuit. If so (step 415: Y), the power access controller115 may deny, in step 425, the device 110 access to the power source135. On the other hand, the power access controller 115, may provide(e.g., grant) the device 110 access to the power source 135 in step 420if the power that the device 110 is expected to consume does not exceedthe available power (step 415: N). Providing access to the power sourcemay include closing a switch in the power access controller 115 and/orthe device 110 to complete the power supply circuit. After grantingaccess to the power source 135, the power access controller 115 mayoptionally switch communications between the controller 115 and device110 from power line communication to another method of communication,such as wireless communication or a separate wired connection (e.g.,Ethernet).

If the power access controller 115 denies the device 110 access to thepower source 135, the controller 115 may determine whether there are anynearby power sources (or outlets/chargers) that the device 110 might beable to access. For example, additional outlets or chargers in the sameroom or in the same structure (but on different circuits) may be used.The controller 115 may display or use a speaker to notify the user ofthe device 110 of the alternative outlet or charger and its location.Additionally or alternatively, the controller 115 may send thisinformation to the device 110 (via the connection 103 or a differentwired or wireless connection), and the device 110 may display thelocation of the alternative outlet or charger. The power accesscontroller 115 (or master power controller 125) may be connected to(e.g., hooked into) a message or event (e.g., bus) system to notify theuser of the alternative outlet or charger. The message in this systemmay be sent to the device 110 via, for example, a text messaging service(e.g., SMS, MMS), email, etc. The message may additionally oralternatively be sent to another device, such as a device in the user'shome automation system, such as a thermostat having a display and/orspeaker. The power access controller 115, the device 110, or anotherdevice may have access to a map or blueprint of the location 105 (ornearby locations) to identify the alternative outlets and chargers.

FIG. 5 illustrates an example method of accounting of power usage for apower-consuming device 110 accessing a power source 135 according to oneor more illustrative aspects of the disclosure. The steps described withrespect to FIG. 5 may be performed by one or more computing devices,such as the power access controller 115, master power controller 125,and/or power source 135. For the sake of convenience, the stepsdescribed with respect to FIG. 5 will generally be described as beingperformed by the power access controller 115.

In step 505, the power access controller 115 may determine the device'spower consumption. In general, any of the devices described with respectto FIG. 1 may determine the amount of power consumed by the device 110.For example, the device 110 may itself determine the amount of powerdrawn from the power source 135. The power source 135 may determine theamount of power the device 110 draws from the source 135. The poweraccess controller 115 and/or master power controller 125 may determinethe amount of power the device 110 consumes by measuring the amount ofpower coming from the power source 135 and/or the amount of power beingsent to the device 110.

The amount of power consumed by the device 110 may be monitored overtime, and information indicating the amount of power consumed may begenerated. For example, as long as the power source 135 supplies powerto the device 110, updates about the device's power consumption may beperiodically submitted, such as to the master power controller 125 orthe power access controller 115, for accounting purposes. The generatedusage information may be used to bill a user associated with the device110 and/or to generate a display of the device's power consumption.

In step 510, the power access controller 115 may determine a userassociated with the device 110. During authentication and/orauthorization, the device 110 may have sent to the power accesscontroller 115 information identifying the user, such as a username,email address, billing address, credit card information, account number,or other information uniquely identifying the user. For example, theuser identifier (e.g., an account number) may be associated with anaccount the user has with the owner, operator, or manager of the powersource 135 or an account the user has for the device 110 (e.g., anInternet Service Provider (ISP) account, a mobile service provider,etc.). If the device 110 did not provide the user's information duringauthentication or authorization, the power access controller 115 mayretrieve the information from a database storing information thatcorrelates the device's identifier (e.g., IMEI, certificate, etc.) to auser. The database may be operated by the owner, operator, or manager ofthe power source 135 and/or an owner, operator, or manager of a serviceprovided to the device 110 (e.g., mobile service provider, ISP, etc.).

In step 515, the power access controller 115 may generate a bill for theuser for the device's power consumption. If the user has an account withthe provider of the power source 135, the user's account may be directlybilled (e.g., monthly or bi-monthly) for the amount of power consumed bythe device 110 over the billing period. For example, if the user plugsthe device 110 into an outlet at the user's home, the user's residentialpower provider account can be directly billed. Similarly, if the userplugs the device into an outlet at a neighbor's home and the neighboruses the same residential provider, the user's account with theresidential power provider can be directly billed.

If the user does not have an account with the power provider, a new billfor the amount of power consumed may be generated and sent (e.g., byphysical mail or electronic communications, such as email) to the user.Additionally or alternatively, the bill may be sent to a third-partybroker that oversees billing of power consumption for one or more powerproviders. The third-party broker may apply the bill to an account theuser has with the broker. Using the billing method described herein, auser may plug in or otherwise charge a device 110 at any location, suchas an airport, a parking lot, a friend's house, etc., and have theuser's own account be billed for the power consumed.

In step 520, the power access controller 115 may generate a display ofthe device's power consumption and/or a display of the overall powerconsumption of devices at a particular location, such as the user'shome, an airport, a parking garage with electric vehicle chargers, etc.The display may indicate the amount of power consumed by each device ata particular location, such as the user's home 105. The display mayindicate the amount of power consumed by each category of device at thelocation 105. As previously described, categories include mobile device,household appliance, vehicle, etc. The display may also indicate theamount of power consumed by devices at the location 105 by manufacturer,such as the power consumption of devices manufactured by Manufacturer A,devices manufactured by Manufacturer B, and devices manufactured byManufacturer C. The power access controller 115 may display the powerconsumption on a display, such as a display integrated in the controller115, a display in the device 110 (e.g., a vehicle display or a mobilephone display), a television display (e.g., in the user's home), acomputer display, etc. Accordingly, the aspects described herein mayprovide for power metering, analysis, and visualization. For example,the user may see the percentage of monthly power consumption or billthat each device, category of device, or manufacturer contributes to theoverall monthly power consumption or bill.

Users may also receive credit for off-peak power consumption and/orcharging. For example, users that charge or connect their devicesbetween 1 AM and 5 AM may receive a credit or discount on their powerbills. Moreover, a power provider may be permitted to manage and controlpower flow to individual devices across their network to manage thepower grid while minimizing inconvenience to users.

In step 525, the power access controller 115 may determine whether thedevice's power consumption exceeds the expected power consumptionidentified in the device's power profile. If the device's consumptiondoes not exceed the expected power consumption (step 525: N), the poweraccess controller 115 may proceed to step 530.

In step 530, the power access controller 115 may determine whetheranother parameter in the device's power profile has been exceeded. Aspreviously explained, other parameters may include normal, minimum,and/or maximum operating voltages, fuse or breaker type, fuse or breakerrating (e.g., in volts and/or amps), status of the fuse (e.g.,operational, triggered, needs replacing, etc.), and the like. The otherparameters may have been included in the device's power profile, or thepower access controller 115 may have retrieved the other parameters froma database, such as a device manufacturer's database.

In one example, the power access controller 115 may determine whetherthe device's operating voltage has exceeded its maximum operatingvoltage indicated in the power profile. If so (step 530: Y), the poweraccess controller 115 may proceed to step 535 to deny the device 110access to the power source 135. As another example, the power accesscontroller 115 may determine the status of a protection device of thedevice 110, such as a fuse or a breaker. If the fuse or breaker isoperational, the power access controller 115 may continue to grant thedevice 110 access to the power source 135. On the other hand, ifinformation from the device 110 indicates that the fuse or breakershould be replaced or has tripped, the power access controller 115 mayprevent access to the power source 135. As yet another example, assumethat DC power is being provided to the device 110. The power accesscontroller 115 may monitor the level of noise in the circuit for thepower supply 135. If the level of noise exceeds a threshold, such as theline noise immunity level for device 110, the power access controller115 may deny access to the power source 135 in step 535. The aboveexamples are non-limiting, and the power access controller 115 maymonitor any of the operating parameters described herein and use themonitored parameter to determine whether to continue to provide power tothe device 110 or to deny the device 110 access to power.

If the device's consumption exceeds the expected power consumption (step525: Y) or another parameter in the power profile has been exceeded(step 530: Y), the power access controller 115, in step 535, may denythe device 110 access to the power source 135. For example, assume thatthe power profile of a laptop 110 indicated that the peak powerconsumption of the laptop is 100 watts. The power access controller 115may grant the laptop 110 a tolerance of 5%, so that the laptop's peakpower consumption can rise up to 105% before the power access controller115 denies the laptop 110 access to the power source 135. The poweraccess controller 115 may open a switch or otherwise break the circuitproviding power to the device 110. The power access controller 115 mayalternatively send an instruction to the device 110 to stop accessingthe power source 135.

The device 110 can be prevented from accessing the power source 135 viaother methods. For example, the user may send, from his or her mobiledevice, an instruction to the power access controller 115 or masterpower controller 125 to stop power from flowing to the device 110. Theuser's location may also be tracked (e.g., based on the location of oneor more of the user's devices), and power can turned off when the userleaves the location 105. For example, power to the appliances 110 at theuser's home 105 may be shut off if the user leaves the home 105. Powerline communication may also be used to prevent access to the powersource 135. For example, the master power controller 125 or power source135 may send, via a power line, an instruction to the power accesscontroller 115 to prevent the device 110 from accessing the power source135. Similarly, the power access controller 115 may communicate with thedevice 110 via a power line and request the device 110 to stop accessingthe power source 135. Power may shut off if the device 110 isdisconnected from the power access controller 115.

The various features described above are merely non-limiting examples,and can be rearranged, combined, subdivided, omitted, and/or altered inany desired manner. For example, features of the computing device(including the remote control device and the terminal device) describedherein can be subdivided among multiple processors and computingdevices. The true scope of this patent should only be defined by theclaims that follow.

The invention claimed is:
 1. A non-transitory computer-readable storagemedium storing instructions that, when executed by one or moreprocessors, cause: receiving, from a user device, a device profileassociated with the user device; determining, based on the deviceprofile associated with the user device, an expected power consumptionof the user device; determining, based on the expected power consumptionof the user device, whether the user device is authorized to access apower source; and granting, based on determining that the user device isauthorized to access the power source, the user device access to thepower source.
 2. The non-transitory computer-readable storage medium ofclaim 1, wherein the device profile associated with the user deviceindicates at least one of: a device identifier of the user device, amanufacturer of the user device, or a category of the user device. 3.The non-transitory computer-readable storage medium of claim 1, whereinthe instructions, when executed by the one or more processors, cause thedetermining whether the user device is authorized to access the powersource further based on determining whether devices categorized in acategory of the user device are authorized to access the power source.4. The non-transitory computer-readable storage medium of claim 1,wherein the instructions, when executed by the one or more processors,cause the determining whether the user device is authorized to accessthe power source further based on determining, based on the expectedpower consumption of the user device, whether a circuit of the powersource would be overloaded if the user device is granted access to thepower source.
 5. The non-transitory computer-readable storage medium ofclaim 1, wherein the expected power consumption of the user devicecomprises a rated power consumption of the user device or a historicalpower consumption of the user device.
 6. The non-transitorycomputer-readable storage medium of claim 1, wherein the instructions,when executed by the one or more processors, cause the determiningwhether the user device is authorized to access the power source furtherbased on determining whether the expected power consumption of the userdevice exceeds a threshold power consumption.
 7. The non-transitorycomputer-readable storage medium of claim 1, wherein the instructions,when executed by the one or more processors, cause the receiving thedevice profile based on the user device being connected to a poweroutlet or a charger.
 8. A non-transitory computer-readable storagemedium storing instructions that, when executed by one or moreprocessors, cause: receiving, from a user device, a device profileassociated with the user device, wherein the device profile associatedwith the user device indicates a device identifier of the user device;determining, based on the device identifier of the user device, whetherthe user device is authorized to access a power source; and granting,based on determining that the user device is authorized to access thepower source, the user device access to the power source.
 9. Thenon-transitory computer-readable storage medium of claim 8, wherein thedevice profile associated with the user device further indicates amanufacturer of the user device, and wherein the instructions, whenexecuted by the one or more processors, cause the determining whetherthe user device is authorized to access the power source further basedon the manufacturer of the user device.
 10. The non-transitorycomputer-readable storage medium of claim 8, wherein the device profileassociated with the user device further indicates a category of the userdevice, and wherein the instructions, when executed by the one or moreprocessors, cause the determining whether the user device is authorizedto access the power source further based on the category of the userdevice.
 11. The non-transitory computer-readable storage medium of claim8, wherein the instructions, when executed by the one or moreprocessors, cause the receiving the device profile based on the userdevice being connected to a power outlet or a charger.
 12. Thenon-transitory computer-readable storage medium of claim 8, wherein theinstructions, when executed by the one or more processors, further causedetermining, based on the device profile associated with the userdevice, an expected power consumption of the user device, and whereinthe instructions, when executed by the one or more processors, cause thedetermining whether the user device is authorized to access the powersource further based on the expected power consumption of the userdevice.
 13. The non-transitory computer-readable storage medium of claim12, wherein the expected power consumption of the user device comprisesa rated power consumption of the user device or a historical powerconsumption of the user device.
 14. The non-transitory computer-readablestorage medium of claim 12, wherein the instructions, when executed bythe one or more processors, cause the determining whether the userdevice is authorized to access the power source further based ondetermining whether the expected power consumption of the user deviceexceeds a threshold power consumption.
 15. An apparatus comprising: oneor more processors; and memory storing instructions that, when executedby the one or more processors, cause the apparatus to: receive, from auser device, a device profile associated with the user device;determine, based on the device profile associated with the user device,an expected power consumption of the user device; determine, based onthe expected power consumption of the user device, whether the userdevice is authorized to access a power source; and grant, based ondetermining that the user device is authorized to access the powersource, the user device access to the power source.
 16. The apparatus ofclaim 15, wherein the device profile associated with the user deviceindicates at least one of: a device identifier of the user device, amanufacturer of the user device, or a category of the user device. 17.The apparatus of claim 15, wherein the instructions, when executed bythe one or more processors, cause the apparatus to determine whether theuser device is authorized to access the power source further based ondetermining whether devices categorized in a category of the user deviceare authorized to access the power source.
 18. The apparatus of claim15, wherein the instructions, when executed by the one or moreprocessors, cause the apparatus to determine whether the user device isauthorized to access the power source further based on determining,based on the expected power consumption of the user device, whether acircuit of the power source would be overloaded if the user device isgranted access to the power source.
 19. The apparatus of claim 15,wherein the expected power consumption of the user device comprises arated power consumption of the user device or a historical powerconsumption of the user device.
 20. The apparatus of claim 15, whereinthe instructions, when executed by the one or more processors, cause theapparatus to determine whether the user device is authorized to accessthe power source further based on determining whether the expected powerconsumption of the user device exceeds a threshold power consumption.21. The apparatus of claim 15, wherein the instructions, when executedby the one or more processors, cause the apparatus to receive the deviceprofile based on the user device being connected to a power outlet or acharger.
 22. An apparatus comprising: one or more processors; and memorystoring instructions that, when executed by the one or more processors,cause the apparatus to: receive, from a user device, a device profileassociated with the user device, wherein the device profile associatedwith the user device indicates a device identifier of the user device;determine, based on the device identifier of the user device, whetherthe user device is authorized to access a power source; and grant, basedon determining that the user device is authorized to access the powersource, the user device access to the power source.
 23. The apparatus ofclaim 22, wherein the device profile associated with the user devicefurther indicates a manufacturer of the user device, and wherein theinstructions, when executed by the one or more processors, cause theapparatus to determine whether the user device is authorized to accessthe power source further based on the manufacturer of the user device.24. The apparatus of claim 22, wherein the device profile associatedwith the user device further indicates a category of the user device,and wherein the instructions, when executed by the one or moreprocessors, cause the apparatus to determine whether the user device isauthorized to access the power source further based on the category ofthe user device.
 25. The apparatus of claim 22, wherein theinstructions, when executed by the one or more processors, cause theapparatus to receive the device profile based on the user device beingconnected to a power outlet or a charger.
 26. The apparatus of claim 22,wherein the instructions, when executed by the one or more processors,further cause the apparatus to determine, based on the device profileassociated with the user device, an expected power consumption of theuser device, and wherein the instructions, when executed by the one ormore processors, cause the apparatus to determine whether the userdevice is authorized to access the power source further based on theexpected power consumption of the user device.
 27. The apparatus ofclaim 26, wherein the expected power consumption of the user devicecomprises a rated power consumption of the user device or a historicalpower consumption of the user device.
 28. The apparatus of claim 26,wherein the instructions, when executed by the one or more processors,cause the apparatus to determine whether the user device is authorizedto access the power source further based on determining whether theexpected power consumption of the user device exceeds a threshold powerconsumption.
 29. A system comprising: a user device; and a computingdevice comprising: one or more processors; and memory storinginstructions that, when executed by the one or more processors of thecomputing device, cause the computing device to: receive, from the userdevice, a device profile associated with the user device, wherein thedevice profile associated with the user device indicates a deviceidentifier of the user device; determine, based on the device identifierof the user device, whether the user device is authorized to access apower source; and grant, based on determining that the user device isauthorized to access the power source, the user device access to thepower source, wherein the user device comprises: one or more processors;and memory storing instructions that, when executed by the one or moreprocessors of the user device, cause the user device to: send, to thecomputing device, the device profile associated with the user device.30. The system of claim 29, wherein the device profile associated withthe user device further indicates a manufacturer of the user device, andwherein the instructions stored in the memory of the computing device,when executed by the one or more processors of the computing device,cause the computing device to determine whether the user device isauthorized to access the power source further based on the manufacturerof the user device.
 31. The system of claim 29, wherein the deviceprofile associated with the user device further indicates a category ofthe user device, and wherein the instructions stored in the memory ofthe computing device, when executed by the one or more processors of thecomputing device, cause the computing device to determine whether theuser device is authorized to access the power source further based onthe category of the user device.
 32. The system of claim 29, wherein theinstructions stored in the memory of the computing device, when executedby the one or more processors of the computing device, cause thecomputing device to receive the device profile based on the user devicebeing connected to a power outlet or a charger.
 33. The system of claim29, wherein the instructions stored in the memory of the computingdevice, when executed by the one or more processors of the computingdevice, further cause the computing device to determine, based on thedevice profile associated with the user device, an expected powerconsumption of the user device, and wherein the instructions stored inthe memory of the computing device, when executed by the one or moreprocessors of the computing device, cause the computing device todetermine whether the user device is authorized to access the powersource further based on the expected power consumption of the userdevice.
 34. The system of claim 33, wherein the expected powerconsumption of the user device comprises a rated power consumption ofthe user device or a historical power consumption of the user device.35. The system of claim 33, wherein the instructions stored in thememory of the computing device, when executed by the one or moreprocessors of the computing device, cause the computing device todetermine whether the user device is authorized to access the powersource further based on determining whether the expected powerconsumption of the user device exceeds a threshold power consumption.36. A system comprising: a user device; and a computing devicecomprising: one or more processors; and memory storing instructionsthat, when executed by the one or more processors of the computingdevice, cause the computing device to: receive, from the user device, adevice profile associated with the user device; determine, based on thedevice profile associated with the user device, an expected powerconsumption of the user device; determine, based on the expected powerconsumption of the user device, whether the user device is authorized toaccess a power source; and grant, based on determining that the userdevice is authorized to access the power source, the user device accessto the power source, wherein the user device comprises: one or moreprocessors; and memory storing instructions that, when executed by theone or more processors of the user device, cause the user device to:send, to the computing device, the device profile associated with theuser device.
 37. The system of claim 36, wherein the device profileassociated with the user device indicates at least one of: a deviceidentifier of the user device, a manufacturer of the user device, or acategory of the user device.
 38. The system of claim 36, wherein theinstructions stored in the memory of the computing device, when executedby the one or more processors of the computing device, cause thecomputing device to determine whether the user device is authorized toaccess the power source further based on determining whether devicescategorized in a category of the user device are authorized to accessthe power source.
 39. The system of claim 36, wherein the instructionsstored in the memory of the computing device, when executed by the oneor more processors of the computing device, cause the computing deviceto determine whether the user device is authorized to access the powersource further based on determining, based on the expected powerconsumption of the user device, whether a circuit of the power sourcewould be overloaded if the user device is granted access to the powersource.
 40. The system of claim 36, wherein the expected powerconsumption of the user device comprises a rated power consumption ofthe user device or a historical power consumption of the user device.41. The system of claim 36, wherein the instructions stored in thememory of the computing device, when executed by the one or moreprocessors of the computing device, cause the computing device todetermine whether the user device is authorized to access the powersource further based on determining whether the expected powerconsumption of the user device exceeds a threshold power consumption.42. The system of claim 36, wherein the instructions stored in thememory of the computing device, when executed by the one or moreprocessors of the computing device, cause the computing device toreceive the device profile based on the user device being connected to apower outlet or a charger.